Release 10.1A: OpenEdge Development:
Web Services

Session models for Web services

The Web service session model affects client access to Web services as follows:

Session managed — The Web service client maintains a persistent connection to the AppServer, maintaining session context between requests for a single client application. This allows a client to carry out complex transactions that span multiple requests, but often requires extra code management, on the part of the client, for each request.
Session free — The Web service client sends requests without any connection to an AppServer. This allows more clients to simultaneously access the Web service with minimal code management, but each request returns a complete result that has no certain dependency on the results of any previous requests.
Note: Session-free Web services using ProcObjects can maintain limited session context across multiple requests, but ProcObjects are not recommended for use by session-free Web services. For more information, see the "How session models affect Web service objects" section.